Jetty throws exception after `java -jar start.jar`?

There are 2 possibilities that stand out as the most likely cause.

There are 2 possibilities that stand out as the most likely cause: The server configuration file (jetty. Xml) that you're using does not match the version of Jetty that you're using. The versions do match, but the setThreadPool method is throwing an exception which is being lost The 2nd seems more likely, so you should follow the instructions on this page docs.codehaus.org/display/JETTY/Debugging to turn on "ignored exception" logging.

I expect you'll find that an exception is being throw during the call to "Server. SetThreadPool" and that is being "ignored" and treated as a "NoSuchMethod" exception.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.